Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1699

reference
656-tree-1
name
1699
tree-preservation-order

undefined

656-tpo-1
uprn
address-text
point
POINT (-1.006400 50.863443)
geometry
MULTIPOLYGON (((-1.006259 50.863428,-1.006265 50.863456,-1.006285 50.863481,-1.006316 50.863501,-1.006355 50.863515,-1.006399 50.863519,-1.006443 50.863515,-1.006483 50.863503,-1.006514 50.863483,-1.006535 50.863458,-1.006543 50.863431,-1.006536 50.863403,-1.006517 50.863378,-1.006486 50.863357,-1.006446 50.863344,-1.006403 50.863339,-1.006359 50.863343,-1.006319 50.863356,-1.006287 50.863376,-1.006266 50.863400,-1.006259 50.863428)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL